Example: Development Case

Topics

• About the Development Case Sample
• Overview of the Development Case
• Iteration Workflows
• Business Engineering
• Requirements
• Analysis & Design
• Implementation
• Testing
• Deployment
• Configuration & Change Management
• Project Management
• Environment

About the Development Case Sample

This is a sample of what a development case may look like. There is no point in restating information that already is in the process. Deviations from the process is what you have to describe. You may put together a Development Case that contains a small description of the process. The problem with that kind of document is that they tend to grow, grow for ever, until they are in the size of the process handbook!

This sample is intended to give you an idea of how a development case would look for a small project, a commercial information system.

For more information about the Development Case, its contents and outline, see Artifact: Development Case.

Overview of the Development Case

To ensure that you understand the material presented here, you should first read

• "The Rational Unified Process - An Introduction". This will give you a general overview and an understanding of the process representation.
• For the details of the workflows, see the Rational Unified Process.

Core Workflows

The development-case sample presented here takes you through all nine core workflows: Business Engineering, Requirements, Analysis & Design, Implementation, Test, Deployment, Configuration & Change Management, Project Management, and Environment.

Artifacts

An artifact is a deliverable of the process. It is often developed within one core workflow, though there are exceptions. Artifacts are organized in seven artifact sets. To describe how an artifact should be used, we use the following terminology:

• To be skipped: this artifact is not required in this specific process.
• Casual: this artifact is created and used as work information, it is not reviewed and approved by anyone because it is often a temporary artifact that is discarded after the project is complete.
• Informal: the artifact is used in the process but it is informal. It is not delivered, and maybe never defined on paper, but someone has approved it.
• Formal-Internal: the artifact is formally produced and used internally at a specific milestone.
• Formal-External: the artifact is part of a delivery at a specific milestone, and requires some form of approval by the buyer, the customer, or some other external stakeholder.

Project Use

This section describes how you should use the development case in a project. For information on how to organize and control a project, see the Project Management workflow.

The core workflows can be applied to almost any project model. For this to be done, the following plans must be formulated.

• Software Development Plan. The layout over the of the four phases (Inception, Elaboration, Construction, and Transition), and a specification of what will be achieved at each major milestone and when. This is called a phase plan and is captured in one section of the Software Development Plan. The breaking down of phases in iterations, and the "contents" of each iteration.
• Iteration Plan. The organization of each iteration.

Each iteration consists of work done in all core workflows, but in varying proportions depending on where the iteration is in the software lifecycle. Early iterations focus on requirements and architectural analysis, whereas late iterations focus more on design, implementation, and testing. The figure below illustrates typical proportions. Thus, part of the Iteration Plan is to decide how the various core workflows are to be exercised for each iteration.

The process is organized both in time (phases, iterations) and content (core workflows).

You should use the development case in parallel with the Iteration Plan for each iteration. The development case tells specifically what parts of each model you have chosen to use in your project.

Iteration Workflows

Inception Workflows

• Early Inception Iteration

Elaboration Workflows

To be defined later in the project.

Construction Workflows

To be defined later in the project.

Transition Workflows

To be defined later in the project.

Business Engineering

Artifacts

Reports

Key Input Artifacts

Configuration Items

• The business object model.
• The Glossary.

Workflow

• Follow the Domain Modeling workflow detail only, see the "Business Engineering Overview".

Requirements

Artifacts

Reports

Key Input Artifacts

Configuration Items

• The Vision document
• The Stakeholder Requests document
• The use-case model.
• All use-case storyboards.
• All boundary classes.
• Each use-case package.
• Each use case will be CM handled as one unit consisting of a document file, a model file, and a snapshot file.
• Supplementary Specification.
• The Glossary.
• The Software Architecture Document.

Maintenance of "Input Requirements"

• Not necessary, keep it as is.

Workflow

• No changes. For details on the process, see the "Requirements Overview".

Analysis & Design

Artifacts

Reports

Key Input Artifacts

Configuration Items

• The design model.
• Each design package.
• Each class.
• Each use-case realization.
• The Software Architecture Document.

Workflow

• We are not developing a real-time application, therefore the Capsule Designer worker and the activity Capsule Design are excluded. For details on the workflow, see the "Analysis & Design Overview".

Implementation

Artifacts

Key Input Artifacts

Configuration Items

• The implementation model.
• Each implementation subsystem.
• Each component.
• The Integration Build Plan.

Code reviews

Informal reviews of all code.

Unit Test Coverage

• See the test plan.

Workflow

• No changes in the workflow. For details on the process, see the "Implementation Overview".

Testing

Artifacts

Key Input Artifacts

Configuration Items

All test artifacts are configuration items.

Test Approval Criteria

• Test cases - Informally approved by the system testers.
• Test procedures - casual.
• The system testers decide if the test criteria for an iteration is fulfilled.
• The customer approves the final iteration.

Workflow

• No formal performance test is done, otherwise the workflow is followed unchanged. For details on the process, see the "Test Overview".

Deployment

Artifacts

Key Input Artifacts

Configuration Items

All deployment artifacts are configuration items.

Workflow

A previously existing deployment workflow has been adapted to use the artifacts suggested in the Rational Unified Process. An exception is the Course Material artifact, which is excluded since no formal training is produced for our product.

Configuration & Change Management

Artifacts

Key Input Artifacts

Configuration Items

All configuration and change management artifacts are configuration items.

Workflow

No changes in the workflow. For details on the process, see the "Configuration & Change Management Overview".

Project Management

Artifacts

Key Input Artifacts

None defined.

Configuration Items

All management artifacts are configuration items.

Workflow

A previously existing deployment workflow has been adapted to use the artifacts suggested in the Rational Unified Process. An exception is the Course Material artifact, which is not developed since no formal training is produced for our product.

Environment

Artifacts

Key Input Artifacts

None defined.

Configuration Items

All environment artifacts are configuration items.

Workflow

No changes in the workflow. For details on the process, see the "Environment Overview".